docs: clarify AssetAlias usage#67392
Conversation
potiuk
added
the
ready for maintainer review
| Dynamic data events emitting and asset creation through AssetAlias | ||
| ----------------------------------------------------------------------- | ||
| An asset alias can be used to emit asset events of assets with association to the aliases. Downstreams can depend on resolved asset. This feature allows you to define complex dependencies for Dag executions based on asset updates. | ||
| Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset URI is |
There was a problem hiding this comment.
| Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset URI is | |
| Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset attributes (i.e., URI, name) are |
There was a problem hiding this comment.
imo we should not use "i.e.". What about
Use
AssetAliaswhen a task must declare an asset dependency before the Asset's fixed attributes (like URI or name) are available.
There was a problem hiding this comment.
as lone as we use both name and uri, I'm good 👀
| ----------------------------------------------------------------------- | ||
| An asset alias can be used to emit asset events of assets with association to the aliases. Downstreams can depend on resolved asset. This feature allows you to define complex dependencies for Dag executions based on asset updates. | ||
| Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset URI is | ||
| known. The alias is listed in ``outlets`` as a stable name, and the task resolves it at runtime by |
There was a problem hiding this comment.
What does "stable name" mean? What does "concrete" mean?
| Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset URI is | ||
| known. The alias is listed in ``outlets`` as a stable name, and the task resolves it at runtime by | ||
| adding one or more concrete ``Asset`` objects through ``outlet_events`` or yielded ``Metadata``. | ||
| Downstream Dags can depend on the alias, and Airflow triggers them when events are emitted for the |
There was a problem hiding this comment.
"trigger" is kind of an overloaded term in Airflow. Maybe we should say "...and Airflow initiates a Dag run when..."
|
@Will-thom can you resolve open conversations? |
|
@Will-thom I've removed the Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. If you have questions, an Apache Airflow maintainer — a real person — is happy to help. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you. |
potiuk
removed
the
ready for maintainer review
7 participants
Closes #52250. Clarifies when to use AssetAlias: when the concrete asset URI is only known at runtime, while the task still needs to declare a stable outlet dependency. Validation: git diff --check for airflow-core/docs/authoring-and-scheduling/assets.rst and targeted text search.
Important
🛠️ Maintainer triage note for @Will-thom · by
@potiuk· 2026-07-02 17:46 UTCSome review feedback from
@Lee-W,@RNHTTRis waiting on you:@Lee-W,@RNHTTRneed a reply or a fix.The ball is in your court — you've been assigned to this PR. Reply or push a fix in each thread, then mark them resolved.
Automated triage — may be imperfect; a maintainer takes the next look.